Default to latest Python patch versions#34
Merged
TheJulianJES merged 1 commit intozigpy:mainfrom Jan 30, 2026
Merged
Conversation
Contributor
Author
|
If we go with this, this is also something we want to adjust in other projects where we currently pin specific versions. The upsides of this change would be that we no longer need to keep all patch versions in the individual projects updated. See further explanation in #33. |
Contributor
Author
|
This should be good to go. I'll update all repo workflows that specify their own CI Python versions later. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Defaults to latest Python patch versions.
Additional information
This actually works now. The linked PR caused different jobs in the workflow to always have the latest Python patch version if not pinned to a specific patch version already, even if the latest patch version is not cached in the GitHub runner (which is what previously caused failures/venv cache key misses):
check-latestforsetup-pythonaction #33